<?xml version="1.0" encoding="utf-8"?>
<Content xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:blueonionsoftware-com:bloget:runtime:data">
  <text>
		&lt;p&gt;
		&lt;/p&gt;
		&lt;p&gt;This post tests Bloget with &lt;a href="http://www.anconia.com/rocketpost/"&gt;RocketPost2&lt;/a&gt;. Actually, this blog editor gave me a quite a bit of difficulty. Unlike other blog editors, sends the password as a base64 string. Not a bad idea but again, not standard either. That’s what testing is for I suppose. It has some rather unique features that are a bit of fun. You have already seen one of them, the Drop Cap style (well you would if I could get it to post). Another cool feature is something called a pull quote. Just highlight a section and click the button and you get one of those quotes in a block with larget letters. Makes for some nice effects. &lt;img height="83" hspace="5" src="http://blueonionsoftware.com/Blog/Images/blogcglogo_8.png" width="172" align="left" vspace="5" border="0" /&gt;&lt;/p&gt;
		&lt;p&gt;It has the usual image uploading and handeling features plus the ability to define margins and borders. A nice touch. Other image formatting options including tinting, film graining cropping and dithering (image at left was cropped and film grained). Just enough to spice up your images without having to go to an external program. One note about the image uploading. Like many offline blog editors, RocketPost uses the metaWeblog.newMediaObject API. However, like the passwords, it is non-standard in that it does not pass the media type as required by the &lt;a href="http://www.xmlrpc.com/metaWeblogApi"&gt;MetaWeblog RFC&lt;/a&gt;. &lt;/p&gt;
		&lt;p&gt;Adding tags like &lt;a href="http://www.technorati.com/tag/Bloget"&gt;Bloget &lt;/a&gt;is a snap and it supports a dozen different services out of the box. It’s a bit pricy at $99 however. &lt;/p&gt;
		&lt;p&gt;After playing with this some more I beginning to realize just how buggy this thing is. Their metaWeblog implementation has all sorts of strange anonmilies like adding a text node to the &lt;params&gt;tag. It can be worked around but it sure would be easier if they followed the RFC more closely.  What can’t be worked around is it does not send a newPost. Everytime I to publish a new post, it tries to send it as an metaWeblog.editPost. That’s just not going to work. Finally, while they sometimes use base64 for passwords, other times it is just passed as a string value. The lack of consistency is really annoying. I don’t get a good feeling about this product and given their complete lack of compliance I can’t see supporting it. Bummer. Some great ideas but lousy execution. I finally gave up and posted this entry with Windows Live Writer because of the problems.&lt;/params&gt;&lt;/p&gt;
</text>
  <last_update>2007-07-25T02:56:23.65625Z</last_update>
  <source_title />
  <source_link />
  <comments />
  <references />
  <attachments />
</Content>